home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000024_icon-group-sender_Tue Sep 10 07:50:47 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id g8AEoiU10589
for icon-group-addresses; Tue, 10 Sep 2002 07:50:44 -0700 (MST)
Message-Id: <200209101450.g8AEoiU10589@baskerville.CS.Arizona.EDU>
Subject: Re: Using Procedure Names for Debugging
From: Steve Graham <Steve_Graham@labcorp.com>
To: Icon Group <icon-group@cs.arizona.edu>
Date: 10 Sep 2002 08:33:07 -0500
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
As a number of you kindly pointed out, the invocable directive needed to
be added to my program to enable this technique with non-builtins.
Thanks to all who so quickly responded.
Steve
===
On Mon, 2002-09-09 at 12:35, Steve Graham wrote:
> While developing an Icon program, I wanted an easy way to debug each
> procedure. I had read that there is more than 1 way to invoke a
> command. For example, you can have the statement write(5) or you can
> have "write"(5). I figured that I would use this idea to develop a test
> module, to which I would pass a procedure name and arguments. The test
> module would in turn invoke the specified procedure as in the 2nd
> example above with the arguments and report back the results, if any.
> However, I wasn't able to make it work. I'd bet there is a way,
> though. Any ideas?
>
> TIA, Steve
>
>
--
Steve
---------------------------------------------------------------------------------------
Steve Graham
Lead Project Analyst/Engineer
LabCorp
Phone: (972) 643-6124
Fax: (972) 454-1050
Mail: Steve_Graham@labcorp.com
---------------------------------------------------------------------------------------